home *** CD-ROM | disk | FTP | other *** search
- Path: rapidnet.com!wblock
- From: wblock@rapidnet.com (Warren Block)
- Newsgroups: comp.sys.amiga.hardware
- Subject: Re: Problems with Quantum Atlas XP34300
- Date: 29 Jan 1996 16:22:43 GMT
- Organization: RapidNet
- Message-ID: <4eis8j$6ps@rapidnet.com>
- References: <4ebd1m$eob@hobbes.lyseo.otol.fi>
- NNTP-Posting-Host: rapidnet.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- Jari Ketola (allas@lyseo.otol.fi) wrote:
- : I recently bought an Quantum Atlas XP34300 harddisk and
- : encountered problems shortly after formating it. I was
- : adviced to format the drive with the following parameters:
-
- : 4096 Cylinders
- : 32 Heads
- : 64 Block per Track
- : 2048 Blocks per Cylinder
-
- : in order to obtain exactly the 2^32 byte limit.
-
- Fred Fish has reported problems with using 4G partitions (which may or
- may not apply to your situation). It would be worth making the drive
- into two 2G partitions.
-
- : The drive
- : suggested different values, but I didn't pay any attention
- : to them because I was told that it's OK to do so with
- : SCSI drives.
-
- : The drive worked just fine but right after putting the
- : computer case back and rebooting the machine problems started.
- : When several users (I run a BBS) accessed the same partition
- : simultaneously the whole system hung. When I checked the partition
- : with disksalv, the same thing happened. On a "random block"
- : (80000-100000 I guess) in either hash check or the preliminary
- : scan, the disksalv just froze and didnt respond to anything.
- : I had to disable the "Auto mount" option for the partition in order
- : to get the system boot to WB again. I even tried lowering the
- : maxtransfer to 0xffff, but it had little effect.
-
- : I would appreciate any suggestions that might help me solve
- : this problem. I have an A3000/030 (I dont know the buster
- : etc. revisions) with all the scsi devices (Seagate Hawk
- : 1G, Seagate 'Whatever' 660Mb and Quantum Atlas 4G) installed
- : in a separate tower case connected to A3k via a 2m (6.6ft)
- : long ribbon-cable.
-
- Okay, here's just a list of what comes to mind in no particular order:
-
- * Unshielded ribbon cable could be picking up noise. Try a shielded
- external SCSI cable, or maybe just a shorter length of ribbon.
-
- * Check termination, then check it again. It looks like there are no
- internal SCSI devices on the A3000, and so it should have the motherboard
- terminators in place, because it is one end of the SCSI bus.
-
- * If the drive that is at the end of the bus uses passive termination,
- switch it with one of the other drives that has active termination, which
- can make a noticeable difference.
-
- * If your SCSI controller chip (WD 33C93) is rev -04, it's best to
- replace it with the -08.
-
- --
- .----------------------------------------------------------------.
- | Warren R. Block * New EMail Address: wblock@rapidnet.com |
- | Rapid City SD USA * Brought to you in majestic INEMASCOP! |
- `----------------------------------------------------------------'
-